Concurrent enablement of encryption on an operational path at a host port

ABSTRACT

A host port is enabled for security. The host port performs Input/Output (I/O) in plaintext on a path between the host port and a storage port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully. Concurrently with performing of I/O in plaintext on the path, the host port enables encryption of data for I/O on the path.

BACKGROUND 1. Field

Embodiments relate to the concurrent enablement of encryption on an operational path at a host port.

2. Background

Fibre Channel refers to an integrated set of architectural standards for data transfer developed by the American National Standards Institute (ANSI). Security solutions for the Fibre Channel architecture are provided by Fibre Channel Security Protocols (FC-SP) developed by ANSI. FC-SP provides mechanisms for device authentication, per message security, policy distributions, etc., in a Fibre Channel environment. Further details of FC-SP are provided in the publication “Fibre Channel Security Protocols-2 (FC-SP-2)”, Revision 2.71, published on Jun. 12, 2012 by ANSI.

FC-LS-4 provides mechanisms for link services in Fibre Channel and further details are provided in the publication “Fibre Channel Link Services (FC-LS-4)”, Revision 4.04, published on Jul. 16, 2019 by ANSI. FC-FS-5 provides mechanisms for framing and signaling in Fibre Channel and further details are provided in the publication “Fibre Channel Framing and Signaling-5 (FC-FS-5)”, Revision 1.0, published on Apr. 3, 2018 by ANSI.

In a Fibre Channel environment, to provide for secure and encrypted communication between nodes in a Fabric, a Security Association (SA) management transaction occurs between a SA_Initiator and a SA_Responder using a security establishment protocol. The initiator and responders may comprise ports in adaptors in devices in a Fibre Channel network. Separate security associations are established for data transmission and data reception at a port. Completion of the SA establishment transaction results in a set of security associations and related key material used to encrypt/decrypt data communication between the initiator and the responder under the established security association. An example of a security association protocol is the Security Association Management protocol in FC-SP-2. The protocol is comprised of a pair of messages, SA_Init and SA_Init Response to establish a parent association followed by a pair of messages, SA_Auth and SA_Auth Response to perform authentication of the entitles and establish the Security Associations that protect the data transferred between the entities.

A storage controller may control access to storage for one or more host computational devices that may be coupled to the storage controller over a Fibre Channel network. A storage management application that executes in the storage controller may manage a plurality of storage devices, such as disk drives, tape drives, flash drives, direct access storage devices (DASD), etc., that are coupled to the storage controller. A host computational device may send Input/Output (I/O) commands to the storage controller and the storage controller may execute the I/O commands to read data from the storage devices or write data to the storage devices. The communication between the hosts and the storage controller occur via Fibre channel ports located on adapters in the hosts and the storage controller.

US patent publication 20100154053 discusses a storage security mechanism using cryptographic splitting. US patent publication 20190251282 discusses a cyber security mechanism for transferring data between servers. US patent publication 20160139845 discusses storage level access control for data grouping structures. US patent publication 20160378691 discusses mechanisms for protecting a storage against an attack. U.S. Pat. No. 8,275,950 discusses a Fiber Channel Connection storage controller that may manage the one-to-one correspondence of ports of the host computers and the storage controller using a log-in request control table to prevent any unauthorized access attempts from host computers on a port-by-port basis thereby maintaining enhanced security. U.S. Pat. No. 6,219,771 discusses a data storage apparatus with improved security process and partition allocation functions. US patent publication 20040107342 discusses a secure network file access control system. European patent application EP1276034A2 discusses security for logical unit in a storage subsystem. US patent publication 20160342798 discusses a system and method for protected device management. U.S. Pat. No. 8,799,436 discusses a system and method for auditing and verifying configuration items in an information technology (IT) configuration management database.

U.S. Pat. No. 6,832,313 describes a system including a central computer and a remote computer, which can communicate over a link, and is migrated from in-clear working to encrypted working, as the computers receive and install long term keys necessary for encrypted communication. U.S. Pat. No. 8,250,625 describes a method for reducing communication system downtime when enabling cryptographic operation of a cryptographic system of the communication system where the cryptographic system includes a first cryptographic device operatively coupled to a plurality of second cryptographic devices via a communication network of the communication system.

SUMMARY OF THE PREFERRED EMBODIMENTS

Provided are a method, a system, a computer program product in which a host port is enabled for security. The host port performs Input/Output (IO) in plaintext on a path between the host port and a storage port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully. Concurrently with performing of I/O in plaintext on the path, the host port enables encryption of data for I/O on the path. As a result, mechanisms are provided for transitioning from plaintext data to encrypted data in embodiments in which an audit mode indicator is enabled.

In certain embodiments, the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the host port and the storage port. As a result, mechanisms are provided to allow the embodiments to be implemented in conjunction with Fibre Channel security associations.

In further embodiments, the host port is programmed with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path. As a result, encrypted data is allowed from certain points in time.

In certain embodiments, in response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the host port is configured for both plaintext reception and for encrypted data reception using the key material. As a result, a new indicator is used to allow intermixed plaintext and encrypted data.

In further embodiments, in response to the host port determining that all plaintext reception has completed because of an expiry of a timer after a security association has been activated for transmission the host port is programmed to no longer handle plaintext data. As a result, transition from mixed plaintext and encrypted data to only encrypted data takes place.

In yet further embodiments, the timer expires after a timeout period that is sufficient to flush plaintext data that was queued for transmission of the path at a time transmission of the encrypted data started on the path. As a result, sufficient time is allowed for all queued plaintext I/O to complete.

In further embodiments, no I/O errors are generated when both plaintext data and encrypted data are exchanged in the path during a predetermined time period indicated by a timer. As a result, the audit mode in integrated into Fibre Channel without causing I/O errors.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers represent corresponding parts throughout:

FIG. 1 illustrates a block diagram of a heterogeneous computing environment comprising a plurality of hosts that communicate over a Fibre Channel Fabric to a plurality of storage controllers and/or storage devices, in accordance with certain embodiments;

FIG. 2 illustrates a block diagram of a system for maintaining access for a host for security enablement in a heterogeneous computing environment, in accordance with certain embodiments;

FIG. 3 illustrates a block diagram that shows a security bit for login in Fibre Channel and an enhancement to Fibre Channel via an audit mode indicator, in accordance with certain embodiments;

FIG. 4 illustrates a block diagram that shows a login and a response in Fibre Channel, in accordance with certain embodiments;

FIG. 5 illustrates a block diagram than shows an enhancement to Fibre Channel to provide indications for “security enforced” and “security enabled” via enablement or non-enablement of an audit mode indicator, in accordance with certain embodiments;

FIG. 6 illustrates a flowchart that shows operations of a security enforced storage port, in accordance with certain embodiments;

FIG. 7 illustrates a flowchart that shows operations of a security enabled storage port, in accordance with certain embodiments;

FIG. 8 illustrates a block diagram that shows conditions preventing authentication and security association management from being successfully completed, in accordance with certain embodiments;

FIG. 9 illustrates a block diagram that shows a plurality of host ports logging in into a single storage port, in accordance with certain embodiments;

FIG. 10 illustrates flowchart that shows operations in a storage device for determining whether to change a storage port to a security enforced status, in accordance with certain embodiments, in accordance with certain embodiments;

FIG. 11 illustrates flowchart that shows operations for maintaining access for security enablement on a host system, in accordance with certain embodiments, in accordance with certain embodiments;

FIG. 12 illustrates flowchart that shows additional operations for maintaining access for security enablement on a host system, in accordance with certain embodiments;

FIG. 13 illustrates flowchart that shows operations for maintaining access for security enablement in a storage device, in accordance with certain embodiments;

FIG. 14 illustrates flowchart that shows additional operations for maintaining access for security enablement in a storage device, in accordance with certain embodiments;

FIG. 15 illustrates a block diagram that shows a transition from plaintext I/O to encrypted I/O after authentication and security association has successfully completed in embodiments in which audit mode has been enabled, in accordance with certain embodiments:

FIG. 16 illustrates a block diagram that shows data structures for allowing a grace time period for plaintext I/O to continue when encrypted I/O starts over a path, in accordance with certain embodiments;

FIG. 17 illustrates a block diagram that shows the start of plaintext I/O over a path, in accordance with certain embodiments;

FIG. 18 illustrates a block diagram that shows the flow from “plaintext I/O” to “Mixed plaintext I/O and encrypted I/O” to “encrypted I/O” over a path, in accordance with certain embodiments;

FIG. 19 illustrates flowchart that shows operations for concurrent enablement of encryption on an operational path at a host port, in accordance with certain embodiments:

FIG. 20 illustrates flowchart that shows operations for concurrent enablement of encryption on an operational path at a storage port, in accordance with certain embodiments;

FIG. 21 illustrates a block diagram of a cloud computing environment, in accordance with certain embodiments;

FIG. 22 illustrates a block diagram of further details of the cloud computing environment of FIG. 21, in accordance with certain embodiments; and

FIG. 23 illustrates a block diagram of a computational system that shows certain elements that may be included in the hosts, storage controllers and storage devices, as described in FIGS. 1-22, in accordance with certain embodiments.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments. It is understood that other embodiments may be utilized and structural and operational changes may be made.

The standard for encrypting Fibre Channel links (FC-SP-2) includes protocols for mutual authentication of the two endpoints (i.e., ports) as well as protocols for negotiating encryption keys that are used in communication sessions between the two endpoints. The standard provides support for a variety of mechanisms to authenticate the involved parties and as well as mechanisms by which key material is provided or developed.

In the FC-SP-2 standard, support for authentication within an endpoint is indicated by the setting of the Security Bit of the Common Service parameters passed to the peer during the login process. When set to a value of one in the login request, the Security Bit indicates that the sending port is able to perform authentication. When the responding port accepts the login request, if in the reply it also sets the Security Bit to one then this indicates that the responding port requires the sender of the login to now perform authentication before granting any further access.

The FC-SP-2 standard specifies the behavior of the responding endpoint in terms of the acceptance or rejection of the login request and the setting of the Security Bit based on security policy in effect at that endpoint at the time the request is received. The standard makes no provision for how this policy is instantiated at the responding endpoint. In an enterprise datacenter, care needs to be taken to protect access to data as well as provide security for the data. When enabling security in a heterogeneous environment containing some systems and storage ports that do not support security (e.g., legacy ports), certain embodiments provide mechanisms to ensure that connectivity is not lost, in contrast to current standards that do not allow for such mechanisms to be provided.

Certain embodiments provide a mechanism to enable security at a host in an “audit mode” in which access to data by a host is not lost when security is enabled in a storage device. An indication is provided via a setting of an audit mode indicator at the time of login that allows a host port to continue to access a storage port after security is enabled. Once authentication and enablement of security mechanisms is verified to have been completed successfully, security enablement may be changed to a policy of security enforcement. Security enablement means that I/O can be performed even if authentication and enablement of security mechanisms have not completed successfully, while security enforcement means that I/O cannot be performed if authentication and enablement of security mechanisms have not completed successfully. While in audit mode, a host may continue to access the storage device and provide tools to audit the security state of connections.

Certain embodiments provide a mechanism in which a host determines that the authentication and/or security association cannot be successfully completed with a storage device, and then uses the audit mode indicator to check if security is not enforced on the storage port. If the audit mode indicator is set, the host processor continues sending I/O operations to the storage device along the selected port. If the audit mode indicator is not set, then the host processor ceases I/O operations to the storage device and notifies the host application or operating system to find an alternate path to complete the I/O operations.

Additionally, in Fibre Channel, many host ports may login (as described in FC-FS-5) to a single storage port. Some of these host ports may support security and some may not. If a port setting is set to security enforced, the host ports that do not support security may lose access to the storage port as these host ports are not allowed to login.

In certain embodiments, information is provided by the storage device to show the number of current logins to each of its ports. For that number of logins, the storage device provides the number of security capable logins, and the number of logins that are successfully authenticated and have enabled security. From this information, it can be determined whether or not access could be lost to a port if the storage port setting is changed to security enforced. Once all logins are determined to be secure, the setting may be changed without access loss as all host ports are able to successfully enable security. In certain embodiments, when the setting is desired to be changed to enforce security, the storage device checks login counters to determine if an access loss could occur (i.e., there are logins that are not successfully authenticated) and prevents the setting from being changed to enforce security.

Certain embodiments provide a storage port that supports a setting to enable security without enforcement, and that provides auditable statistics (e.g., login counts, security capable login count, and security enabled login counts) for determining effects of setting security to enforcement. An audit mode indicator is set in a login response to the host port, indicating that I/O can be sent to this storage port even if authentication cannot be completed successfully. The setting of enabled or enforced for security, may be performed on a storage array or on individual storage port basis.

In certain embodiments, provided is a setting for security enforcement having automated checking of the login indicators to prevent changing the setting if access loss could occur. An option to force the setting to security enforcement without regard to login indicators is also provided.

As a result improvements are made to devices to maintain connectivity for performing I/O, in an enhancement to a Fibre Channel based connectivity environment.

The above embodiments enable security at a host in an audit mode in which access to data by a host is not lost when security is enabled on a storage device. An indication is provided at time of login that allows a host port to continue to access a storage port after security is enabled. The access without a security association that enables encryption means that the host and storage ports may be exchanging data in the clear, where exchanging data in the clear means that the exchanged data is not encrypted, and the data exchanged in the clear is referred to as “plaintext” data.

When a security association to enable encryption is successfully created, the host and storage ports need be able to transition from exchanging plaintext data to exchanging “encrypted” data, where encrypted data refers to data that is encrypted. A transition period exists where both plaintext and encrypted data is flowing on the link between the host and storage ports and certain embodiments ensure that such a condition does not cause errors to be detected by security enforcement rules that are put in place by the security association.

Certain embodiments provide mechanisms for a host system to transition from exchanging plaintext to exchanging encrypted data. Such embodiments also provide mechanisms for a storage port to transition from exchanging plaintext to exchanging encrypted data. As a result, further improvements are made to devices to maintain connectivity for performing I/O, in an enhancement to a Fibre Channel based connectivity environment.

Exemplary Embodiments Implementing Audit Mode

FIG. 1 illustrates a block diagram 100 of a heterogeneous computing environment comprising a plurality of hosts 102, 104 that communicate over a Fibre Channel Fabric 106 to a plurality of storage controllers and/or storage devices 108, 110, in accordance with certain embodiments. Both storage controllers and storage devices are shown via reference numeral 108, 110, and the hosts 102, 104 may communicate with storage controllers that control storage devices, or may communicate with storage devices without involvement of any storage controller. A storage controller may also be regarded as an advanced type of storage device since it controls and allows access to one or more storage devices to one or more hosts.

The hosts 102, 104 and the storage controllers 108, 110 may comprise any suitable computational device including those presently known in the art, such as, a personal computer, a workstation, a server, a mainframe, a hand held computer, a palm top computer, a telephony device, a network appliance, a blade computer, a processing device, a controller, etc. Storage devices may include storage device presently known in the art, such as hard disk drives, tape drives, solid state drives, etc.

The hosts 102, 104 and the storage devices 108, 110 may be elements in any suitable network, such as, a storage area network, a wide area network, the Internet, an intranet. In certain embodiments, the hosts 102, 104 and the storage devices 108, 110 may be elements in a cloud computing environment. The connectivity between the hosts 102, 104 and the storage devices 108, 110 in the network and/or cloud computing environment may be over the Fibre Channel Fabric 106.

A host may include one or more host ports. For example, host 102 includes a plurality of host ports 112, and host 104 includes a plurality of host ports 114. A storage device may include a plurality of storage ports. For example, storage device 108 includes a plurality of storage ports 116, and storage device 110 includes a plurality of storage ports 118. The host ports 112, 114 and the storage ports 116, 118 may be in communication over the Fibre Channel Fabric 106.

In certain embodiments, not all hosts support security for host ports. For example, certain legacy hosts may not support security for host ports in Fibre Channel, or certain legacy adapters in hosts may not support security for host ports in Fibre Channel. For example, host 102 is shown as supporting security for a host port, and host 104 is shown as not supporting security for a host port.

In certain embodiments, certain storage devices may enable one or more storage ports to be configured as enabling security with enforcement (i.e., I/O may not occur from a host port to a storage port unless secure connectivity has been verified as being completed between the host port and the storage port). In certain embodiments, certain storage devices may enable one or more storage ports to be configured as enabling security without enforcement (i.e., I/O may occur from a host port to a storage port even if secure connectivity has not been verified as being completed between the host port and the storage port). For example, storage device 108 may have enabled security with enforcement for at least one of the storage ports 116 (other storage ports in the storage device 108 may have enabled security without enforcement).). In FIG. 1, storage device 110 may have enabled security without enforcement for at least one of the storage ports 118 (other storage ports in the storage device 110 may have security enabled with enforcement).

Therefore FIG. 1 shows certain embodiments that allow I/O operations to be sent from a host port to a storage port even if authentication or security association negotiation between and host port and a storage port cannot be completed successfully.

FIG. 2 illustrates a block diagram 200 of a system for maintaining access for a host 202 for security enablement in a heterogeneous computing environment, in accordance with certain embodiments.

The host 202 is communicatively coupled to a plurality of storage devices 204, 206 via a Fibre Channel Fabric 208. The storage device 204 has enabled security with enforcement for storage port 210 of the storage device 204, and the storage device 206 has enabled security without enforcement for storage port 212 of the storage device 206. In certain embodiments, a storage port may be changed from enabling security without enforcement to enabling security with enforcement and vice versa.

The host 202 includes a host port 214, where the host port 214 is in communication with the storage ports 210, 212. In the embodiments shown in FIG. 2, the host port 214 is able to transmit I/O to the storage port 212 even if authentication or security association negotiation between the host port 214 and the storage port 212 cannot be completed successfully, because the storage port 212 has enabled security without enforcement. However, the host port 214 is unable to transmit I/O to the storage port 210 if authentication or security association negotiation between the host port 214 and the storage port 210 cannot be completed successfully, because the storage port 210 has enabled security with enforcement.

In case the host port 214 is unable to transmit I/O operation to a storage port, then the operating system 216 of the host 202 attempts to transmit the I/O operation via another mechanism.

FIG. 3 illustrates a block diagram 300 shows a security bit 302 for login in current Fibre Channel standards and an enhancement to Fibre Channel via an audit mode indicator 304, in accordance with certain embodiments. The audit mode indicator 304 may be enabled (reference numeral 306) or not enabled (reference numeral 308).

It should be noted that the audit mode indicator 304 is not found in existing Fibre Channel standards. The enablement of the audit mode indicator 304 allows enablement of security without enforcement to work in cooperation with the configuration of the security bit 302.

In certain embodiments, the audit mode indicator 304 is enabled via an indication in auxiliary parameter data word 0, bit 23 in programs that implement Fibre Channel Link Services (FC-LS-4). Other mechanisms to implement the audit mode indicator 304 may be provided in other embodiments. The audit mode indicator 304 and the security bit 302 may be part of one or more data structures that are used for performing operations.

FIG. 4 illustrates a block diagram 400 that shows a login and a response in Fibre Channel, in accordance with certain embodiments. A host port 402 transmits a login request 404 to a storage port 406. The host port 402 is also referred to as a “sending port” and the storage port 406 is also referred to as a “receiving port”.

In the login request 404 from the host port 402, the security bit 302 is set to one to indicate that the sending port (i.e., the host port 402) is able to perform authentication.

On receiving the login request 404, the storage port 406 sends a response 408 to the host port 402. The response 408 from the storage port 406 may set the security bit 302 to one to indicate that the receiving port (i.e., the storage port 406) requires the sending port (i.e., the host port 402) to now perform authentication before granting any further access.

In certain embodiments, even if the security bit 302 is set to one in the response, if the audit mode indicator 304 is enabled (i.e., set) to indicate security enabled without enforcement, then the requirement to complete authentication before granting any further access is overridden.

FIG. 5 illustrates block diagram 500 that shows an enhancement to Fibre Channel to provide indications for “security enforced” and “security enabled” via enablement or non-enablement of an audit mode indicator 304, in accordance with certain embodiments.

Indications are provided by a receiving port (e.g. a storage port in a storage device) in the response to a login request from a host post (as shown via reference numeral 502). The indications may be provided via configuration of the audit mode indicator 304. The configuration of the audit mode indicator 304 as enabled may result in a state of a storage port being “security enabled” 504 which means that security is enabled without enforcement. Not enabling the configuration of the audit mode indicator 304 may result in a state of a storage port being “security enforced” 506 which means that security is enabled with enforcement.

FIG. 6 illustrates a flowchart 600 that shows operations of a security enforced storage port, in accordance with certain embodiments. Control proceeds to block 604 in which authentication and security association management is initiated between a host port and the storage port. Control proceeds to block 606 in which a determination is made as to whether authentication and security association management has successfully completed between the host port and the storage port. If so (“Yes” branch 608) control proceeds to block 610 in which the host port is allowed to start performing I/O through the storage port (at block 610). If not (“No” branch 612), control proceeds to block 614 in which the host port is prevented from performing I/O through the storage port.

FIG. 7 illustrates a flowchart 700 that shows operations of a security enabled storage port, in accordance with certain embodiments.

Control starts at block 702 in which security is enabled for a storage port. Control proceeds to block 704 in which authentication and security association management is initiated between a host port and the storage port. The host port is allowed to perform I/O through the storage port (block 706) irrespective of whether or not the authentication and security association management operation completes successfully or unsuccessfully (at block 708). The time at which the I/O starts being allowed may differ in different embodiments.

FIG. 8 illustrates a block diagram 800 that shows conditions preventing authentication and security association management from being successfully completed, in accordance with certain embodiments.

A first condition 802 is an incomplete configuration of security policy that may prevent authentication and security association management from being successfully completed. A second condition 804 comprises inaccessible key servers that provide credentials to access the storage device that may prevent authentication and security association management from being successfully completed. A third condition 806 is a failure in authentication and security association management exchanges that may prevent authentication and security association management from being successfully completed. All these conditions may cause the authentication and security association management from being successfully completed in the operations shown in FIGS. 6 and 7.

FIG. 9 illustrates a block diagram 900 that shows a plurality of host ports 902, 904, 906 logging in into a single storage port 908, in accordance with certain embodiments. The single storage port 908 may be included in a storage device or storage controller 910, where the storage device or storage controller 910 may have other storage ports.

In FIG. 9, the host ports 902 and 906 support security, whereas the host port 904 does not support security as it may be included in a legacy adapter or a legacy host or for some other reason including configuration by an administrator.

The storage device or storage controller 910 maintains statistics on login counters and login characteristics referred to as login indicators (reference numeral 912). The statistics include: a number of current logins to the storage port (reference numeral 914); a number of security capable logins counts to the storage port (reference numeral 916); and a number of security enabled login counts to the storage port (reference numeral 918). The security enabled login are those that have successfully authenticated and have enabled security.

In certain embodiments, the statistics on login counters and login characteristics 912 are used by the storage device or storage controller 910 for determining an effect on I/O access by hosts if the security enforced mode is configured. In additional embodiments, the statistics on login counters and login characteristics 912 are used by the storage device or storage controller to prevent a switchover to the security enforced mode from the security enabled mode if an I/O access is to be lost by a host on switchover to the security enforced mode.

In further embodiments, the storage device or storage controller 910 provides an option 920 to force switchover to the security enforced mode without consideration of the statistics on login counters and login characteristics 912.

FIG. 10 illustrates flowchart 1000 that shows operations in a storage device for determining whether to change a storage port to a security enforced status, in accordance with certain embodiments, in accordance with certain embodiments.

Control starts at block 1002 in which a storage device determines that a plurality of host ports have performed a login to a storage port of the storage device. Control proceeds to block 1004 in which the storage device maintains statistics on login counters and login characteristics. The storage device determines (at block 1006) from the login counters and login characteristics whether any host port would lose access to I/O to the storage device if the setting of the storage port is changed to security enforced. If so (“Yes” branch 1008), not all host ports logins are secure (i.e., not all host ports are successfully authenticated) and control proceeds to block 1010 in which the setting of the storage port is prevented from being changed to security enforced.

If at block 1006 the storage device determines from the login counters and login characteristics that no host port would lose access to I/O to the storage device if the setting of the storage port is changed to security enforced (“No” branch 1012) then all host port logins are secure (i.e., all host ports are successfully authenticated) and control proceeds to block 1014 in which the setting of the storage port is allowed to be changed to security enforced.

FIG. 11 illustrates flowchart 1100 that shows operations for maintaining access for security enablement on a host system, in accordance with certain embodiments, in accordance with certain embodiments.

Control starts at block 1102 in which a host port is enabled for security. A determination is made (at block 1104) by the host port that authentication or security association negotiation with a storage port cannot be completed successfully.

In response to a determination by the host port that authentication or security association negotiation with a storage port cannot be completed successfully, the host port determines (at block 1106) whether an audit mode indicator has been enabled in a login response from the storage port. The host port preserves input/output (I/O) access to the storage port based on determining whether the audit mode indicator has been enabled in the login response from the storage port. As a result, a host port may be able to perform I/O via a storage port even if authentication or security association negotiation with a storage port cannot be completed successfully.

In response to determining that the audit mode indicator has been enabled in the login response from the storage port (“Yes” branch 1108), the host port performs (at block 1110) I/O to the storage port. Performing I/O to the storage port means sending an I/O operation to the storage port for performing an I/O operation in which data is read or written or accessed. As a result, a host port performs I/O via a storage port even if authentication or security association negotiation with a storage port cannot be completed successfully when the audit mode indicator has been enabled.

In response to determining that the audit mode indicator has not been enabled in the login response from the storage port (“No” branch 1112), the host port avoids (at block 1114) performing I/O to the storage port. As a result, a host port does not perform I/O via a storage port if authentication or security association negotiation with a storage port cannot be completed successfully and the audit mode indicator has not been enabled. From block 1114 control proceeds to block 1116 in which the host port returns I/O requests to an operating system of a host computational device. As a result, alternative mechanisms are tried for performing I/O, if authentication or security association negotiation with a storage port cannot be completed successfully and the audit mode indicator has not been enabled.

FIG. 12 illustrates flowchart 1200 that shows additional operations for maintaining access for security enablement on a host system, in accordance with certain embodiments.

The host port determines (at block 1202) that authentication or security association negotiation with the storage port cannot be completed successfully if the host port is unable to access a key server to obtain credentials to authenticate with the storage port. As a result, the host port may take further action to determine a status of the audit indicator to determine whether to send I/O requests to the storage port.

From block 1202 control proceeds to block 1204 in which, the host port determines that authentication or security association negotiation with a storage port cannot be completed successfully if there is a failure in a process for the authentication or the security association negotiation with the storage port. As a result, the host port may take further action to determine a status of the audit indicator to determine whether to send I/O requests to the storage port.

FIG. 13 illustrates flowchart 1300 that shows operations for maintaining access for security enablement in a storage device, in accordance with certain embodiments.

Control starts at block 1302 in which a storage port receives a login request. From block 1302 control may proceed to block 1304 or to block 1306.

In block 1304, the storage port configures the audit mode indicator as enabled in a login response to a host port to enter a security enabled mode to indicate to the host port that Input/Output (I/O) operations are to be transmitted from the host port to the storage port even if authentication or security association negotiation with the storage port cannot be completed successfully. As a result, hosts that are not secure may perform I/O to a storage device.

In block 1306, the storage port configures the audit mode indicator as not enabled in a login response to the host port to enter a security enforced mode to indicate to the host port that I/O operations are not to be transmitted from the host port to the storage port if authentication or security association negotiation with the storage port cannot be completed successfully. As a result, hosts that are not secure are unable to perform I/O to a storage device.

FIG. 14 illustrates flowchart 1400 that shows additional operations for maintaining access for security enablement in a storage device.

Control starts at block 1402 a storage controller that includes the storage port maintain statistics on login counters and login characteristics including: a number of current logins to the storage port; a number of security capable logins counts to the storage port; and a number of security enabled login counts to the storage port. As a result, in certain embodiments, the statistics on login counters and login characteristics are used by the storage controller for determining an effect on I/O access by hosts if the security enforced mode is configured.

In additional embodiments, the statistics on login counters and login characteristics are used by the storage controller to prevent (at block 1404) a switchover to the security enforced mode from the security enabled mode if an I/O access is to be lost by a host on switchover to the security enforced mode. As a result, switchover to security enforced mode is prevented if a host would lose I/O access.

In certain embodiments, the storage controller provides an option to force switchover to the security enforced mode without consideration of the statistics on login counters and login characteristics.

In certain embodiments a storage controller configures at least one storage port of the plurality of storage ports to the security enforced mode. The storage controller configures at least one another storage port of the plurality of storage ports to the security enabled mode. Therefore, enablement of audit mode indicator is on a per port basis.

In further embodiments, the storage port is included in a storage controller that includes a first storage array and a second storage array, wherein the security enforced mode is configured for the first storage array, and wherein the security enabled mode is configured for the second storage array. Therefore, enablement of audit mode indicator is on a per storage array basis.

Therefore, FIGS. 1-14 illustrate certain embodiments to enforce or not enforce security based on configuration of an audit mode indicator to augment operations based on the configuration of the security bit in Fibre Channel. As a result, legacy devices are able to continue with I/O in a heterogeneous computing environment even when the security bit is enabled in Fibre Channel.

Exemplary Embodiments for Plaintext to Encrypted Data Transition

In Fibre Channel, to enable encryption on a link, a Security Association (SA) is established between an SA Initiator and a SA Responder using an SA establishment protocol. An example of an SA Initiator is a Fibre Channel initiator (e.g., host port 112, 114) in host bus adapter (HBA) of a host computational device 102, 104. An example of an SA Responder is a Fibre Channel target port (e.g. storage port 116, 118) in a storage controller 108, 110. In Fibre Channel, separate security associations are established for data transmission and data reception at a port.

The SA establishment protocol is comprised of a series of messages passed between two entities (such a host port and a storage port in a Fibre Channel SAN). An example of such protocol is the Security Association Management protocol in the Fibre Channel Security Protocol Standard FC-SP-2.

The protocol includes of a pair of messages, SA_Init and SA_Init Response to establish a parent association followed by a pair of messages, SA_Auth and SA_Auth Response to perform authentication of the entities and establish the Security Associations that protect the data transferred between the entities.

A first set of security associations (SA1) is established the first time the SA establishment protocol is executed on a path (e.g., a Fibre Channel N_Port login). The set of security associations comprise transmit key material (Klt) and receive key material (Klr). Key material may be comprised of both keys and SALTs (SALT is random data that is used as an additional input to a one-way function that “hashes” data used in encryption mechanisms) and are simply referred to as keys throughout the disclosure. Note that each side has a set of “transmit key material” (Klt) that are equivalent to the “receive key material” (Klr) of the other.

At specific points in the protocol, a port is programmed to begin allowing reception of data using Klr and transmitting data using K it. In certain embodiments, the selection of these points in the protocol is such that reception keys Kr are programmed before the other port in the association may begin transmission of data using that key.

The programming of the new keys to the port for reception of data is done after verification of the SA Auth messages. For the target (e.g., storage port), this is after processing the SA_Auth request message. For the initiator (e.g., host port) this is upon reception of the SA_Auth Response. After the authentication transaction completes successfully, queuing of I/O requests that transmit data begin to use the new SA1. For the target, this can be done only after the SA_Auth Response has been received by the initiator. Reception of the SA_Auth Response at the initiator is confirmed when the target receives the LS_ACC extended link services (ELS) response. For the initiator, this occurs on the reception of Auth_Done.

After completion of a SA establishment operation, both initiator port and target port have begun queuing I/O for transmission using the new transmission keys. However, in certain embodiments, there may still be I/O in the queue or in the SAN that was queued for transmission prior to the SA establishment using plaintext I/O. In order to avoid errors in reception, the ports continue to allow reception of plaintext for some period of time before SA1 encryption can be enforced. This period of time is provided by a timer that may be referred to as a “plaintext grace period timer”. The timer is set to expire after a predefined predetermined period of time (e.g., 2 seconds).

When in transition from plaintext to encryption, in certain embodiments a “plaintext allowed indicator” is enabled and is provided to the data receiver upon programming of the security association for reception of data. This indicator instructs the data receiver (or firmware controlling the data receiver) to allow a mix of encrypted data frames and unencrypted data frames.

At some point, once it is verified that all plaintext I/O has been flushed from system, the data receiver is be reprogramed to reset the allow plaintext indicator. At this point, the data receiver allows reception of encrypted data and does not allow reception of plaintext data. This may accomplished by waiting for timer to expire since the time the SA1 security key material was activated for transmission of data.

FIG. 15 illustrates a block diagram 1500 that shows a transition from plaintext I/O to encrypted I/O after authentication and security association has successfully completed in embodiments in which audit mode has been enabled, in accordance with certain embodiments.

In FIG. 15, arrow 1502 indicates the passage of time while performing I/O over a path between a host port and a storage port. In other words, the time is increasing in the direction the arrow is pointing.

Initially, plaintext I/O (i.e., unencrypted I/O) 1504 is sent over the path established between the host port and the storage port. Once successful completion of authentication and security association has completed (reference numeral 1506), then encrypted I/O 1506 is performed. However there is an overlapping period (shown via reference numeral 1508) in which both plaintext I/O and encrypted I/O are concurrently performed (i.e., plaintext and encrypted I/O are interspersed). In certain embodiments, plaintext I/O is allowed to continue for a predetermined period of time to complete I/Os that were queued but not transmitted prior to successful completion of authentication and security association.

FIG. 16 illustrates a block diagram 1600 that shows data structures for allowing a grace time period for plaintext I/O to continue when encrypted I/O starts over a path, in accordance with certain embodiments.

In addition to the security bit 302 and the audit mode indicator 304 described in FIG. 3, a plaintext allowed indicator 1602 and a plaintext grace period timer 1604 are provided. The plaintext allowed indicator 1602 when enabled (e.g., by being set to a value of 1) allow interspersed encrypted and plaintext data on the path even after successful completion of authentication and security association. The plaintext grace period timer 1604 indicates a period of time (e.g., 2 seconds) for which plaintext data is allowed on the path after encrypted data is allowed on the path. The period of time is sufficient to sufficient to flush plaintext data that was already queued when encrypted I/O started over the path.

FIG. 17 illustrates a block diagram 1700 that shows the start of plaintext I/O over a path, in accordance with certain embodiments.

A SA_Initiator such as a host port (shown via reference numeral 1702) sends a port login (PLOGI 1704) to a SA_Repsonder such as a storage port (shown via reference numeral 1706). On receiving the PLOGI 1704, the storage port 1706 sends a link services accept message (LS_ACC 1708) to the host port 1702, and LS_ACC 1708 is received by the host port 1702. The host port 1702 may be included in a host and the storage port 1706 in a storage controller.

A process login (PRLI 1710) is then sent from the host port 1702 to the storage port 1706. The storage port 1706 receives the PRLI 1710 and sends a link services accept message (LS_ACC 1712) to the host port 1702, where the LS_ACC 1712 is received by the host port 1702. Plaintext I/O starts on the path between the host port 1702 and the storage port 1706 at this time as shown via reference numerals 1714. Reference numeral 1716 shows plaintext I/O being performed on the path.

FIG. 18 illustrates a block diagram 1800 that shows an embodiment of operations for a flow from “plaintext I/O” to “Mixed Plaintext I/O and Encrypted I/O to “Encrypted I/O” occurring between a host port 1702 and a storage port 1706. In one embodiment, the host port 1702 acts as the initiator and the storage port 1706 acts as the responder. It is understood that audit mode is enabled.

To initiate operations to establish a security association, the host port 1702 sends a security association initialization message (SA_Init 1804) from host port 1702 to the storage port 1706 to establish a security association with the storage port 1706 including key material used to create an encryption key. Upon receiving the security association initialization message, the storage port 1706 sends an acceptance of the security association initialization message for processing to the host port 1702. In Fibre Channel protocol implementations, an “accept” for processing a message may take the form of the link services accept message (LS_ACC 1806). After the accept is sent, the storage port 1706 sends an initialization response message (SA_Init Resp 1808) to the host port 1702 to accept the security association, including a selected transform method to use for encryption/decryption. The security association initialization message may include a plurality of different encryption transform methods from which the storage port 1706 may select to use for the security association being established.

Upon receiving the sent initialization response message (SA_Init Resp 1808), the host port 1702 sends an accept (LS_ACC 1810) to the storage port 1706 that the initialization response message is accepted for processing and then sends an authentication message (SA_Auth 1812) to the storage port 1706 to request the storage port 1706 to establish authentication between the storage port 1706 and the host port 1702.

Upon receiving the security association authentication message (SA_Auth 1812), the storage port 1706 sends an accept message (LS_ACC 1814) to the host port 1702 indicating that the authentication message was accepted for processing and then programs a security association SA1 for receive, including a key Klr with a plaintext allowed indicator being set to 1 (as show by reference numeral 1816).

After programming the storage port 1706 with the security association SA1 for the storage port 1706, the storage port 1706 sends an authentication response message (SA_Auth Resp 1818) to the host port 1702 to accept the authentication.

Upon receiving the security association authentication response message, the host port 1702 programs a security association SA1 for receive, including a key Klr with a plaintext allowed indicator being set to 1 (as show by reference numeral 1820). After programming the security association SA1, the host port 1702 sends an accept (LS_ACC 1822) to the storage port 1706 that the authentication message is accepted for processing.

Upon receiving accept 1822, the storage port 1706 activates the security association SA1 for transmit with the key Klt (shown via reference numeral 1824) and starts a timer 1826 to indicate beginning of transmission of encrypted data from the storage port 1706 to the host port 1702. The storage port 1706 starts transmitting encrypted data at this point and the timer 1826 starts counting down from a predetermined value. The timer 1826 is an instantiation of the plaintext grace period timer 1604 shown in FIG. 16.

After activating the security association SA1, the storage port 1706 sends an authentication done message (AUTH Done 1828) to the host port 1702 indicating that both security association initialization and authentication is completed and transmissions may now be encrypted and decrypted for the newly established security association SA1.

Upon receiving the authentication done message, the host port 1702 activate the created security association SA1 for transmit with the key Klt (as shown by reference numeral 1830). After activating the security association SA, the host port 1702 sends an accept (LS_ACC 1832) to the storage port 1706 that the security association SA1 is activated and starts transmitting encrypted I/O to the storage port and starts a timer 1834 to countdown from a predetermined value. The timer 1834 is an instantiation of the plaintext grace period timer 1604 shown in FIG. 16, and in certain embodiments the predetermined value for timers 1834 and 1836 may be the same.

In FIG. 18, from the point in time at which timer 1826 starts counting down, while encrypted data is transmitted from the storage port 1706, plaintext data in queues are also transmitted. In FIG. 18, from the point in time at which timer 1834 starts counting down, while encrypted data is transmitted from the host port 1702, plaintext data in queues are also transmitted from the host port 1702.

Once timer 1826 expires (i.e., the predetermined period of time has expired), plaintext I/O is no longer supported by the storage port 1706 (as shown via reference numeral 1836. Once timer 1834 expires (i.e., the predetermined period of time has expired), plaintext I/O is no longer supported by the host port 1702 (as shown via reference numeral 1838). In such conditions, the plaintext allowed indicator is set to 0.

The predetermined time period for expiry of timers 1826, 1834 is set sufficiently high such that all pending plaintext I/O in queues are flushed at the point in time 1840 and the there is a transition from “intermixed plaintext and SAI encrypted I/O” 1840 to “SA encrypted” I/O 1844.

Therefore, FIG. 18 shows a transition from plaintext I/O 1716, to mixed plaintext and encrypted I/O 1842, to encrypted I/O 1844 over the path between the host port 1702 and the storage port 1706. This allows all pending plaintext I/O to be flushed from queues after authentication and security association has been established successfully. The hatching and cross hatchings show the periods for the different types of data transmission in FIG. 18.

FIG. 19 illustrates flowchart that shows operations for concurrent enablement of encryption on an operational path at a host port, in accordance with certain embodiments.

Control starts at block 1902 in which a host port is enabled for security. The host port performs (at block 1904) Input/Output (I/O) in plaintext on a path between the host port and a storage port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully.

From block 1904 control proceeds to block 1906 in which concurrently with performing of I/O in plaintext on the path, the host port enables encryption of data for I/O on the path, and in certain embodiments, the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the host port and the storage port.

From block 1906 control proceeds to block 1908 in which in response to the host port determining that all plaintext reception has completed because of an expiry of a timer after a security association has been activated for transmission the host port is programmed to no longer handle plaintext data. It should be noted that the timer expires after a timeout period that is sufficient to flush plaintext data that was queued for transmission of the path at a time transmission of the encrypted data started on the path.

In the context of performing embodiments shown in FIG. 19, the host port is programmed with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path.

In response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the host port is configured for both plaintext reception and for encrypted data reception using the key material. Furthermore, no I/O errors are generated when both plaintext data and encrypted data are exchanged in the path during a predetermined time period indicated by a timer.

FIG. 20 illustrates flowchart 2000 that shows operations for concurrent enablement of encryption on an operational path at a storage port, in accordance with certain embodiments;

Control starts at block 2002 in which a storage port is enabled for security. The storage port performs (at block 2004) Input/Output (I/O) in plaintext on a path between the storage port and a host port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the storage port and the host port cannot be completed successfully.

From block 2004 control proceeds to block 2006 in which concurrently with performing of I/O in plaintext on the path, the storage port enables encryption of data for I/O on the path, and in certain embodiments, the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the storage port and the host port.

From block 2006 control proceeds to block 2008 in which in response to the storage port determining that all plaintext reception has completed because of an expiry of a timer after a security association has been activated for transmission, the storage port is programmed to no longer handle plaintext data. It should be noted that the timer expires after a timeout period that is sufficient to flush plaintext data that was queued for transmission of the path at a time transmission of the encrypted data started on the path.

In the context of performing embodiments shown in FIG. 20, the storage port is programmed to with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path. In response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the storage port is configured for both plaintext reception and for encrypted data reception using the key material. Furthermore, no I/O errors are generated when both plaintext data and encrypted data are exchanged in the path during a predetermined time period indicated by a timer.

Therefore, FIGS. 1-20 provide mechanisms for a host system to transition from exchanging plaintext to exchanging encrypted data by allowing a period of time in which intermixed plaintext and encrypted data are exchanged in embodiments in which an audit mode indicator is enabled. Such embodiments also provide mechanisms for a storage port to transition from exchanging plaintext to exchanging encrypted data by allowing a period of time in which intermixed plaintext and encrypted data are exchanged in embodiments in which an audit mode indicator is enabled.

Cloud Computing Environment

Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

Referring now to FIG. 21 an illustrative cloud computing environment 50 is depicted. Security enforcement or enablement and transition to encryption (shown via reference numeral 52) is performed in the cloud computing environment 50. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 21 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 22, a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 21) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 22 are intended to be illustrative only and embodiments of the invention are not limited thereto.

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes, in one example IBM ZSERIES* systems; RISC (Reduced Instruction Set Computer) architecture based servers, in one example IBM PSERIES* systems; IBM XSERIES* systems; IBM BLADECENTER* systems; storage devices; networks and networking components. Examples of software components include network application server software, in one example IBM WEBSPHERE* application server software; and database software, in one example IBM DB2* database software. * IBM, ZSERIES, PSERIES, XSERIES, BLADECENTER, WEBSPHERE, and DB2 are trademarks or registered trademarks of International Business Machines Corporation registered in many jurisdictions worldwide.

Virtualization layer 62 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers; virtual storage; virtual networks, including virtual private networks; virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal provides access to the cloud computing environment for consumers and system administrators. Service level management provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 66 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation; software development and lifecycle management; virtual classroom education delivery; data analytics processing; transaction processing; and security enforcement or enablement and transition to encryption 68 as shown in FIGS. 1-21.

Additional Embodiment Details

The described operations may be implemented as a method, apparatus or computer program product using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. Accordingly, aspects of the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the embodiments may take the form of a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present embodiments.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present embodiments may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present embodiments.

Aspects of the present embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instruction.

FIG. 23 illustrates a block diagram that shows certain elements that may be included in the computational devices, the hosts, the storage controllers, the storage devices, or other devices shown in FIGS. 1-22, in accordance with certain embodiments. The system 2300 may include a circuitry 2302 that may in certain embodiments include at least a processor 2304. The system 2300 may also include a memory 2306 (e.g., a volatile memory device), and storage 2308. The storage 2308 may include a non-volatile memory device (e.g., EEPROM, ROM, PROM, flash, firmware, programmable logic, etc.), magnetic disk drive, optical disk drive, tape drive, etc. The storage 2308 may comprise an internal storage device, an attached storage device and/or a network accessible storage device. The system 2300 may include a program logic 2310 including code 2312 that may be loaded into the memory 2306 and executed by the processor 2304 or circuitry 2302. In certain embodiments, the program logic 2310 including code 2312 may be stored in the storage 2308. In certain other embodiments, the program logic 2310 may be implemented in the circuitry 2302. One or more of the components in the system 2300 may communicate via a bus or via other coupling or connection 2314. Therefore, while FIG. 23 shows the program logic 2310 separately from the other elements, the program logic 2310 may be implemented in the memory 2306 and/or the circuitry 2302.

Certain embodiments may be directed to a method for deploying computing instruction by a person or automated processing integrating computer-readable code into a computing system, wherein the code in combination with the computing system is enabled to perform the operations of the described embodiments.

The terms “an embodiment”, “embodiment”, “embodiments”. “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

Further, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described does not necessarily indicate a requirement that the steps be performed in that order. The steps of processes described herein may be performed in any order practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

At least certain operations that may have been illustrated in the figures show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified or removed. Moreover, steps may be added to the above described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. 

What is claimed is:
 1. A method, comprising: enabling a host port for security; performing, by the host port, Input/Output (I/O) in plaintext on a path between the host port and a storage port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully; and concurrently with performing of I/O in plaintext on the path, enabling, by the host port, encryption of data for I/O on the path.
 2. The method of claim 1, wherein the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the host port and the storage port.
 3. The method of claim 2, wherein the host port is programmed with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path.
 4. The method of claim 3, the method further comprising: in response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the host port is configured for both plaintext reception and for encrypted data reception using the key material.
 5. The method of claim 4, the method further comprising: in response to the host port determining that all plaintext reception has completed because of an expiry of a timer after a security association has been activated for transmission, programming the host port to no longer handle plaintext data.
 6. The method of claim 5, wherein the timer expires after a timeout period that is sufficient to flush plaintext data that was queued for transmission of the path at a time transmission of the encrypted data started on the path.
 7. The method of claim 1, wherein no I/O errors are generated when both plaintext data and encrypted data are exchanged in the path during a predetermined time period indicated by a timer.
 8. A system, comprising: a memory; and a processor coupled to the memory, wherein the processor performs operations, the operations comprising: enabling a host port for security; performing, by the host port, Input/Output (I/O) in plaintext on a path between the host port and a storage port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully; and concurrently with performing of I/O in plaintext on the path, enabling, by the host port, encryption of data for I/O on the path.
 9. The system of claim 8, wherein the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the host port and the storage port.
 10. The system of claim 9, wherein the host port is programmed with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path.
 11. The system of claim 10, the operations further comprising: in response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the host port is configured for both plaintext reception and for encrypted data reception using the key material.
 12. The system of claim 11, the operations further comprising: in response to the host port determining that all plaintext reception has completed because of an expiry of a timer after a security association has been activated for transmission, programming the host port to no longer handle plaintext data.
 13. The system of claim 12, wherein the timer expires after a timeout period that is sufficient to flush plaintext data that was queued for transmission of the path at a time transmission of the encrypted data started on the path.
 14. The system of claim 8, wherein no I/O errors are generated when both plaintext data and encrypted data are exchanged in the path during a predetermined time period indicated by a timer.
 15. A computer program product, the computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to perform operations, the operations comprising: enabling a host port for security, performing, by the host port, Input/Output (I/O) in plaintext on a path between the host port and a storage port, in response to determining that an audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully; and concurrently with performing of I/O in plaintext on the path, enabling, by the host port, encryption of data for I/O on the path.
 16. The computer program product of claim 15, wherein the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the host port and the storage port.
 17. The computer program product of claim 16, wherein the host port is programmed with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path.
 18. The computer program product of claim 17, the operations further comprising: in response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the host port is configured for both plaintext reception and for encrypted data reception using the key material.
 19. The computer program product of claim 18, the operations further comprising: in response to the host port determining that all plaintext reception has completed because of an expiry of a timer after a security association has been activated for transmission, programming the host port to no longer handle plaintext data.
 20. The computer program product of claim 19, wherein the timer expires after a timeout period that is sufficient to flush plaintext data that was queued for transmission of the path at a time transmission of the encrypted data started on the path.
 21. The computer program product of claim 15, wherein no I/O errors are generated when both plaintext data and encrypted data are exchanged in the path during a predetermined time period indicated by a timer.
 22. A data structure implemented in a device, the data structure comprising: a security bit, wherein the security bit enables a host port for security; and an audit mode indicator; a plaintext allowed indicator, wherein configuration of the plaintext allowed indicator is used by the device to perform operations, the operations comprising: enabling a host port for security; performing, by the host port, Input/Output (I/O) in plaintext on a path between the host port and a storage port, in response to determining that the audit mode indicator has been enabled to allow I/O even if authentication or security association negotiation between the host port and the storage port cannot be completed successfully; and concurrently with performing of I/O in plaintext on the path, enabling, by the host port, encryption of data for I/O on the path.
 23. The data structure of claim 22, wherein the concurrent enabling of encryption of data comprises initiating a security association (SA) management transaction between the host port and the storage port.
 24. The data structure of claim 23, wherein the host port is programmed with key material for exchange of encrypted data along with a plaintext allowed indicator configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path.
 25. The data structure of claim 24, the operations further comprising: in response to the plaintext allowed indicator being configured to allow exchange of plaintext data on the path concurrently with exchange of encrypted data on the path, the host port is configured for both plaintext reception and for encrypted data reception using the key material. 